Skip to content

Conversation

pnkfelix
Copy link
Contributor

Make FRU respect privacy of all struct fields, mentioned or unmentioned.

This is RFC 736.

Fix #21407.

(Also, partially addresses #6993, but I do not know whether there are other uses of Ident still outstanding; there are no more references to #6993 present in the code base after this commit.)

@rust-highfive
Copy link
Contributor

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be worth a comment (maybe with a pointer to the RFC), clarifying that

  1. The fields that are explicitly mentioned must be public
  2. The rest must also be public as described in RFC #xyz and issue #xyz

@nikomatsakis
Copy link
Contributor

r+ modulo comment

@pnkfelix
Copy link
Contributor Author

@bors r=nikomatsakis 0a0aa11 rollup

@pnkfelix
Copy link
Contributor Author

@bors: r-

@pnkfelix
Copy link
Contributor Author

(need to add //~ ERROR ... to the test file.)

@pnkfelix
Copy link
Contributor Author

@bors r=nikomatsakis 3f5af9f rollup

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Feb 10, 2015
@bors bors merged commit 3f5af9f into rust-lang:master Feb 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Functional record update should respect privacy (or consume a non-Copy source)

5 participants